| Re: [cdt-dev] Managed Build test failures |
|
Thank you for investigating this Marc!
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
Sent: Thursday, 07 May 2015 4:21 PM To: CDT General developers list. Subject: Re: [cdt-dev] Managed Build test failures Alright, the problem started when we switched to platform M7 (I thought I had reverted to M5a, but I hadn't :O).
There was a change in o.e.core.resources to list the content of directories in alphabetical order. Marc-Andre found the relevant bug: "Resource#accept(IResourceProxyVisitor, int, int) should visit files in alphabetic order" http://eclip.se/461838 Keep this in mind as it may affect other situations So, the fix proposed on Gerrit is correct, and those tests should start passing again soon. Marc From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
Sent: May 6, 2015 3:52 PM To: CDT General developers list. Subject: Re: [cdt-dev] Managed Build test failures I've been trying to fix the failing Managed Build tests.
A git bisect didn't help as I kept seeing those tests fail on old commits. I reverted back to an M5a platform, thinking that may be the reason, but that didn't help either. What I'm seeing is that the order of SUBDIRS is inverted now. Could it be some other dependency that has changed outside of CDT? I've pushed a patch to Gerrit to modifies the different tests sources.mk files to match the output we are now getting, and the tests pass. However, I don't know if this is correct or if the bad order indicates something wrong with the Manager Build. Anyone know enough to have a look? https://git.eclipse.org/r/47370 Thanks From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
Sent: May 4, 2015 2:59 PM To: CDT DEV (cdt-dev@xxxxxxxxxxx) Subject: [cdt-dev] Managed Build test failures Hi,
there's been some Managed Build test failures happening for about a week now. Before bisecting to find the commit, I was wondering if someone with knowledge about that area has any ideas? There are printouts coming up like this: ManagedProjectUpdateTests.testProjectUpdate21CPP_Update:253->doTestProjectUpdate:193 File sources.mk does not match its benchmark. expected: "################################################################################# Automatically-generated file. Do not edit!################################################################################O_SRCS := CPP_SRCS := C_UPPER_SRCS := C_SRCS := S_UPPER_SRCS := OBJ_SRCS := ASM_SRCS := CXX_SRCS := C++_SRCS := CC_SRCS := OBJS := C++_DEPS := C_DEPS := CC_DEPS := CPP_DEPS := EXECUTABLES := CXX_DEPS := C_UPPER_DEPS := # Every subdirectory with source files must be described hereSUBDIRS := \. \Functions \" but was: "################################################################################# Automatically-generated file. Do not edit!################################################################################O_SRCS := CPP_SRCS := C_UPPER_SRCS := C_SRCS := S_UPPER_SRCS := OBJ_SRCS := ASM_SRCS := CXX_SRCS := C++_SRCS := CC_SRCS := OBJS := C++_DEPS := C_DEPS := CC_DEPS := CPP_DEPS := EXECUTABLES := CXX_DEPS := C_UPPER_DEPS := # Every subdirectory with source files must be described hereSUBDIRS := \Functions \. \" >>>>>>>>>>>>>>>start diff: <<<<<<<<<<<end diff |