[IMPORTANT] Keeping the build green

It’s a shame, the build is already broken… :cry:

@lissyx, in your first post you mention 3 links:
[1] Mulet builds on integration branch (mozilla-inbound)
Mulet builds on integration branch (mozilla-inbound)
[2] Device builds on integration branch
Device builds on integration branch
[3] Device builds on mozilla-central
Device builds on mozilla-central

For the [2] and [3], there is no “B” (nor green nor orange). Is that normal?

The [1] has a orange B, so the built is broken… “Build ./build-mulet-linux.sh /home/worker/workspace : busted.”

I’ve open a bug dans link it to the bug1245091:
Bug 1285210 - Mulet builds on integration branch (mozilla-inbound)
Please, if it’s not what you are waiting, sait it and the next time I will try to do the correct thing :wink:

That was a good catch, but your logs were not including the real issue, and no link to a failure job, so it’s a bit harder to find from your bug :). Sadly, I already filed the bug 1285157 :slight_smile:

But that’s a good catch anyway, this is what is needed !

Hi!
I know you are working on this bug to make build working.
Just to be sure, we need to “wait” the bug solved before checking regularly that the green is not broke?

What does the differents color means?

  • green: OK
  • orange: broke
  • brown busted (what is it???)

When I look to the the bug 1285157, I really don’t understand what you are doing, so I really don’t know if you are next to solve the bug or not. Where can I found informations to help me understand how to solve the bug?

https://bugzilla.mozilla.org/show_bug.cgi?id=1285157

I have a patch on that night, it builds and boots. All we need is some
review and then yes we can hope the build is green.

So waiting :-/

<
https://ci3.googleusercontent.com/proxy/07Ul_ILysIPO2Wf2zMgTu2ok0YPwQHyAwtfb-97YDV4wyoMrs8ul0caSkP8YMDetGITsOnsjZXJv1NSkNvyJKsrGZ9t5ONB-K3ldG-DWXEiprh1QHkD4FdgdAQPZp3N_2gLHN3KRJwVUosg=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/p/a5b964/45.png>
pl6025
July 8

Hi!
I know you are working on this bug to make build working.
Just to be sure, we need to “wait” the bug solved before checking
regularly that the green is not broke?

What does the differents color means?

  • green: OK
  • orange: broke
  • brown busted (what is it???)

When I look to the the bug 1285157, I really don’t understand what you
are doing, so I really don’t know if you are next to solve the bug or not.
Where can I found informations to help me understand how to solve the bug?

bugzilla.mozilla.org
<
https://ci3.googleusercontent.com/proxy/WUN2wVWFfmFfOmC-lezieXXHxIRo-04LOC03zj0KhaSnblQcn5s-XdD3JiKCVIJQMGDGqu3Fzy7vDQ44xr6CLU7QTArfQQMsFHPQpLXLRA10pON4SOVtgg=s0-d-e1-ft#https://bugzilla.mozilla.org/extensions/OpenGraph/web/bugzilla.png

1285157 – dom/ipc/ContentChild.cpp:631:24: error: no matching function
for call to ‘mozilla::dom::ContentChild::SetTransport(IPC::Channel*&)’


Visit Topic or reply to this email to respond.


In Reply To

<
https://ci5.googleusercontent.com/proxy/awzTLeZSQ4NoIfBlGZA3lo26kZQVVC_BjmANCNdQ4J3ntLbC3OZJIeAQFM53I2NXMRdNwx5dc_wrzQauIPOWKNBxCWTk2WOuGwsP5-7iO_OBAvvokOOWFV5k6nWiczuxCcFLpgrVlO3SS2U=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/l/ecb155/45.png>
lissyx
July 7
That was a good catch, but your logs were not including the real issue,
and no link to a failure job, so it’s a bit harder to find from your bug
:). Sadly, I already filed the bug 1285157 :slight_smile: But that’s a good
catch anyway, this is what is needed !

Well it looks like something else landed yesterday evening and broke the
build even worse with something breaking client.mk :frowning:

I have a patch on that night, it builds and boots. All we need is some
review and then yes we can hope the build is green.

So waiting :-/

<
https://ci3.googleusercontent.com/proxy/07Ul_ILysIPO2Wf2zMgTu2ok0YPwQHyAwtfb-97YDV4wyoMrs8ul0caSkP8YMDetGITsOnsjZXJv1NSkNvyJKsrGZ9t5ONB-K3ldG-DWXEiprh1QHkD4FdgdAQPZp3N_2gLHN3KRJwVUosg=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/p/a5b964/45.png>
pl6025

July 8

Hi!
I know you are working on this bug to make build working.
Just to be sure, we need to “wait” the bug solved before checking
regularly that the green is not broke?

What does the differents color means?

  • green: OK
  • orange: broke
  • brown busted (what is it???)

When I look to the the bug 1285157, I really don’t understand what you
are doing, so I really don’t know if you are next to solve the bug or not.
Where can I found informations to help me understand how to solve the bug?

bugzilla.mozilla.org
<
https://ci3.googleusercontent.com/proxy/WUN2wVWFfmFfOmC-lezieXXHxIRo-04LOC03zj0KhaSnblQcn5s-XdD3JiKCVIJQMGDGqu3Fzy7vDQ44xr6CLU7QTArfQQMsFHPQpLXLRA10pON4SOVtgg=s0-d-e1-ft#https://bugzilla.mozilla.org/extensions/OpenGraph/web/bugzilla.png

1285157 – dom/ipc/ContentChild.cpp:631:24: error: no matching function
for call to ‘mozilla::dom::ContentChild::SetTransport(IPC::Channel*&)’


Visit Topic or reply to this email to respond.


In Reply To

<
https://ci5.googleusercontent.com/proxy/awzTLeZSQ4NoIfBlGZA3lo26kZQVVC_BjmANCNdQ4J3ntLbC3OZJIeAQFM53I2NXMRdNwx5dc_wrzQauIPOWKNBxCWTk2WOuGwsP5-7iO_OBAvvokOOWFV5k6nWiczuxCcFLpgrVlO3SS2U=s0-d-e1-ft#https://discourse.mozilla-community.org/letter_avatar_proxy/v2/letter/l/ecb155/45.png>
lissyx

July 7
That was a good catch, but your logs were not including the real issue,
and no link to a failure job, so it’s a bit harder to find from your bug
:). Sadly, I already filed the bug 1285157 :slight_smile: But that’s a good
catch anyway, this is what is needed !

For the past days, device builds have been broken because of TaskCluster cache level issues, and I cannot do anything about that: https://bugzilla.mozilla.org/show_bug.cgi?id=1285732

The build are green for the link [1] (see post 11) \o/
But for the two others, the is no “B”. Is that normal? What do we follow to know if building are running normaly?

Thanks for your hard work on build process.

“B” symbol might be missing when: you have filtering NOT including tier 3 ; or the device build have not yet been triggered and/or treeherder is still loading data.

So, if I understand well, for the moment, for the links [2] and [3] (see post 10) the device build have not been triggered. Because, the Tier 3 is include and Threeherder seems to have load all its data.

When I click on the link [2] this is what I have:


Has you can see, Tier 3 is activate.

If this link is not good to follow, can you give a good one? Thanks.

Please give links, it’s hard to follow.

I don’t see anywhere where it is missing any build.

Good news, looks like TaskCluster cache issue is now fixed. I have retriggered jobs on central and pine :slight_smile:

1 Like

\o/

And m-c is back on GREEN!

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-searchStr=b2g&filter-tier=1&filter-tier=2&filter-tier=3&selectedJob=4363725

3 Likes

I have updated the first post with autoland links, since we might have mozilla-central breakages coming from that one.

As reported by @asppsa in Telegram

Mozilla-inbound,
B2G Device Image opt Aries Device Image b2g-device-aries-eng/opt Aries(Be)

./shinano-common/extract-files.sh: line 68: adb: command not found
/home/worker/workspace/gecko/dom/media/webrtc/MediaEngineGonkVideoSource.cpp:417:89: error: use of deleted function 'RefPtr::operator T*() const && [with T = mozilla::layers::ImageBridgeChild]'
make[6]: *** [Unified_cpp_dom_media_webrtc0.o] Error 1
make[5]: *** [dom/media/webrtc/target] Error 2
make[5]: *** Waiting for unfinished jobs…
make[4]: *** [compile] Error 2
make[3]: *** [default] Error 2
make[2]: *** [realbuild] Error 2
make[1]: *** [build] Error 2
make: *** [out/target/product/aries/obj/DATA/gecko_intermediates/gecko] Error 2
Return code: 2
failed to build
Running post_fatal callback…
Exiting 2

Bug Open :
https://bugzilla.mozilla.org/show_bug.cgi?id=1302641

1 Like

Thanks, but remember to mark this as blocking bug 1245091

1 Like

effectively forget that step :blush:

1 Like

New bug opened for mulet here.

https://bugzilla.mozilla.org/show_bug.cgi?id=1303243

Matth

OK thanks for this but it looks like this was related to a more general
bustage, trees are green after a couple of backouts :slight_smile:

<
https://ci3.googleusercontent.com/proxy/BDx5AZH6N01E--Jy3-r3TZm7JMXk1EnmZ5tQaO2KlPizNdw7vAIUZbPSwRiU-0eKHKB6NBxL7714sDthsMTnR7nkSpCWqj-t7nMEAl3XhCQFTtvCYHJ8Q4_QkwvTRzoi-pIwYQvCvccf8obmHyFSroqhfoiW43n5oFgKBRR1oJWc=s0-d-e1-ft#https://discourse.mozilla-community.org/user_avatar/discourse.mozilla-community.org/m.ducorps/45/5251_1.png>
m.ducorps M Ducorps
September 16

New bug opened for mulet here.

Bug 1303243 - Mozilla inbound - Mulet build Job failing - Unsuccessful
Execution Steps