Closed Bug 1214403 Opened 9 years ago Closed 7 years ago

comm- mac unit test packaging is not run in the right objdir

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Fallen, Assigned: Fallen)

References

Details

Attachments

(1 file)

Once bug 1195442 is fixed, there will be another failure. IIRC the test packages are run in the base objdir, not in the platform specific sub-directories.
Attached patch Fix - v1Splinter Review
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #8673324 - Flags: review?(rail)
Comment on attachment 8673324 [details] [diff] [review]
Fix - v1

Review of attachment 8673324 [details] [diff] [review]:
-----------------------------------------------------------------

::: process/factory.py
@@ +1517,5 @@
>                           warnOnFailure=False,
>                           ))
> +            project = os.path.basename(self.objdir)
> +            if project in ('i386', 'x86_64'):
> +                pkg_env['MOZ_CURRENT_PROJECT'] = project

I'm not familiar with MOZ_CURRENT_PROJECT. I'd ask glandium (from https://hg.mozilla.org/mozilla-central/diff/ce1c57e03b88/python/mozbuild/mozbuild/base.py#l1.13) about the possible impact.

@@ +1570,5 @@
>              pkg_env = self.env.copy()
>          else:
>              pkg_env = {}
>  
> +        if self.platform.startswith('macosx'):

IS there any reason for this condition specifically for this place? It's not the same above.
Attachment #8673324 - Flags: review?(rail)
(In reply to Rail Aliiev [:rail] from comment #2)
> Comment on attachment 8673324 [details] [diff] [review]
> Fix - v1
> 
> Review of attachment 8673324 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> ::: process/factory.py
> @@ +1517,5 @@
> >                           warnOnFailure=False,
> >                           ))
> > +            project = os.path.basename(self.objdir)
> > +            if project in ('i386', 'x86_64'):
> > +                pkg_env['MOZ_CURRENT_PROJECT'] = project
> 
> I'm not familiar with MOZ_CURRENT_PROJECT. I'd ask glandium (from
> https://hg.mozilla.org/mozilla-central/diff/ce1c57e03b88/python/mozbuild/
> mozbuild/base.py#l1.13) about the possible impact.

MOZ_CURRENT_PROJECT is used in mozbuild to determine the mozconfig location and objdir, see <http://mxr.mozilla.org/comm-central/source/mozilla/python/mozbuild/mozbuild/base.py#168>. If this is not set, then the directory containing i386/ and x86_64/ will be taken for the top objdir, which is why we were getting errors.

I asked ted if this approach is ok beforehand, but it was only a quick question on IRC so it would be nice to get more eyes on it.

 
> > +        if self.platform.startswith('macosx'):
> IS there any reason for this condition specifically for this place? It's not
> the same above.

I matched this with various other lines that use |self.platform.startswith(...)|, using |'name' in self.platform| is far less common in that file. I'm fine either way though.
Flags: needinfo?(mh+mozilla)
This looks fine, but bears the question: why did this work for Firefox mac builds without this?
Flags: needinfo?(mh+mozilla)
I suspect that Firefox mac test builds are run differently and don't use the buildbot code here. I'll give this a spin on staging.
mozbuild.base.ObjdirMismatchException: Objdir mismatch: /builds/slave/tb-c-cen-m64-00000000000000000/build/objdir-tb/i386 != /builds/slave/tb-c-cen-m64-00000000000000000/build/objdir-tb
(In reply to aleth [:aleth] from comment #6)
> mozbuild.base.ObjdirMismatchException: Objdir mismatch:
> /builds/slave/tb-c-cen-m64-00000000000000000/build/objdir-tb/i386 !=
> /builds/slave/tb-c-cen-m64-00000000000000000/build/objdir-tb

This was unrelated, sorry.
Is this related to the current 10.10 opt mozmill failure? OSX xpcshell appears to be working.
(In reply to aleth [:aleth] from comment #8)
> Is this related to the current 10.10 opt mozmill failure? OSX xpcshell
> appears to be working.

Doesn't seem likely, so I assume this bug is resolved wfm?
Flags: needinfo?(philipp)
Depends on: 1195442
Blocks: 1231174
Is this an adequate follow up to bug 1220018 comment 6?
Flags: needinfo?(aleth)
Summary: comm mac unit tests are not run in the right objdir → comm- mac unit tests are not run in the right objdir
(In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment #10)
> Is this an adequate follow up to bug 1220018 comment 6?

No idea, iirc Fallen was going to test this some time ago, not sure what the outcome was or if it's still needed.
Flags: needinfo?(aleth)
Fallen, OSX xpcshell tests currently run in /builds/slave/test/build/tests/xpcshell/tests/toolkit/components/osfile/tests/xpcshell. Is this correct or not?

There are some puzzling xpcshell/mozmill failures that don't happen locally and it would be nice to rule out this as the cause.
This issue is about /builds/slave/tb-c-cen-m64-00000000000000000/build/objdir-tb/i386 vs /builds/slave/tb-c-cen-m64-00000000000000000/build/objdir-tb and IIRC should be occurring during the actual build, where the test package is packaged. If you want to reproduce it, you need to do a mac universal build.

I don't think this relates to the osfile failures.
(In reply to Philipp Kewisch [:Fallen] from comment #13)
> I don't think this relates to the osfile failures.

I'm not so sure about bug 1093012 though.
Flags: needinfo?(philipp)
Summary: comm- mac unit tests are not run in the right objdir → comm- mac unit test packaging is not run in the right objdir
No longer blocks: 1231174
(In reply to aleth [:aleth] from comment #14)
> (In reply to Philipp Kewisch [:Fallen] from comment #13)
> > I don't think this relates to the osfile failures.
> 
> I'm not so sure about bug 1093012 though.

On investigation, turned out to be unrelated.
I think we can close this bug, I believe we've dropped the i386 builds by now.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: