So what happened to Edison??
It seems that something happened today. I could not complete a build on edison branch for meta-cedartrail. I copied it to meta-mycdv, but other than that same, old same old. I tried the standard unchanged SRCREV and also tried the latest.
Error below:
ERROR: Function 'do_validate_branches' failed (see /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 for further information)
ERROR: Logfile of failure stored in: /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 Log data follows:
| ERROR: Function 'do_validate_branches' failed (see /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 for further information)
NOTE: package linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3: task do_validate_branches: Failed
ERROR: Task 720 (/home/jim/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_validate_branches) failed with exit code '1'
Quoted 4 lines · jfabernathy
It seems that something happened today. I could not complete a build on edison branch for meta-cedartrail. I copied it to meta-mycdv, but other than that same, old same old. I tried the standard unchanged SRCREV and also tried the latest.
I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).
Perhaps Josh knows if anything was pushed to edison ?
Cheers,
Bruce
Quoted 23 lines
Error below:
ERROR: Function '
do_validate_branches' failed (see /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 for further information)
ERROR: Logfile of failure stored in:
/build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 Log data follows:
| ERROR: Function 'do_validate_branches' failed (see /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 for further information)
NOTE: package
linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3:
taskdo_validate_branches: Failed
ERROR: Task 720
(/home/jim/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb,do_validate_branches) failed with exit code '1'_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"
Quoted 12 lines · Bruce Ashfield
Quoted 4 lines · jfabernathy
It seems that something happened today. I could not complete a build on edison branch for meta-cedartrail. I copied it to meta-mycdv, but other than that same, old same old. I tried the standard unchanged SRCREV and also tried the latest.
I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).
Quoted 5 lines
Perhaps Josh knows if anything was pushed to edison ?
Cheers,
Bruce
I'm retesting on the tarballs again. If successful I'll try git version of edison. I started today with complete new clone of poky and meta-intel.
Quoted 24 lines
Quoted 22 lines
Error below:
ERROR: Function '
do_validate_branches' failed (see /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 for further information)
ERROR: Logfile of failure stored in:
/build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 Log data follows:
| ERROR: Function 'do_validate_branches' failed (see /build/mycdv-poky/tmp/work/mycdv-poky-linux/linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3/temp/log.do_validate_branches.26787 for further information)
NOTE: package
linux-yocto-3.0.18+git2+59314a3523e360796419d76d78c6f7d8c5ef2593_2+0d19bde053589ca1f8cca8d740c902b06063ccbf-r3:
taskdo_validate_branches: Failed
ERROR: Task 720
(/home/jim/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb,do_validate_branches) failed with exit code '1'_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 15 lines · jfabernathy
Quoted 14 lines · Bruce Ashfield
Quoted 4 lines · jfabernathy
It seems that something happened today. I could not complete a build on edison branch for meta-cedartrail. I copied it to meta-mycdv, but other than that same, old same old. I tried the standard unchanged SRCREV and also tried the latest.
I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there
shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).
Quoted 8 lines
Quoted 5 lines
Perhaps Josh knows if anything was pushed to edison ?
Cheers,
Bruce
I'm retesting on the tarballs again. If successful I'll try git version of edison. I started today with complete new clone of poky and meta-intel.
The Edison branch has been updated today for the upcoming 1.1 release, did you pull the updates?
Other than meta-intel are you using any other layers? I will try and reproduce here.
Regards,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 20 lines · Joshua Lock
Quoted 19 lines · jfabernathy
Quoted 18 lines · Bruce Ashfield
Quoted 4 lines · jfabernathy
It seems that something happened today. I could not complete a build on edison branch for meta-cedartrail. I copied it to meta-mycdv, but other than that same, old same old. I tried the standard unchanged SRCREV and also tried the latest.
I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there
shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).Perhaps Josh knows if anything was pushed to edison ?
Cheers,
Quoted 9 lines
Quoted 4 lines
Quoted 1 line
Bruce
I'm retesting on the tarballs again. If successful I'll try git version of edison. I started today with complete new clone of poky and meta-intel.
The Edison branch has been updated today for the upcoming 1.1 release, did you pull the updates?
Other than meta-intel are you using any other layers? I will try and reproduce here.
I tried some stuff this morning like switching branches, then doing git pulls, etc. I was getting such bad results, I figured I had screwed up. I re-cloned both poky and meta-intel earlier today. Maybe around 12 noon EST.
Quoted 2 lines
Regards,
Joshua
Quoted 33 lines · jfabernathy
Quoted 32 lines · Joshua Lock
Quoted 20 lines · jfabernathy
Quoted 19 lines · Bruce Ashfield
Quoted 7 lines · jfabernathy
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same, old same old. I tried the standard unchanged SRCREV and
also tried the latest.I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there
shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).Perhaps Josh knows if anything was pushed to edison ?
Quoted 7 lines
Quoted 3 lines
Cheers,
Bruce
I'm retesting on the tarballs again. If successful I'll try git version of edison. I started today with complete new clone of poky and meta-intel.
The Edison branch has been updated today for the upcoming 1.1 release, did you pull the updates?
Quoted 8 lines
Quoted 3 lines
Other than meta-intel are you using any other layers? I will try and reproduce here.
I tried some stuff this morning like switching branches, then doing git pulls, etc. I was getting such bad results, I figured I had screwed up. I re-cloned both poky and meta-intel earlier today. Maybe around 12 noon EST.
This sounds like meta-intel and the Edison updates aren't getting along. Just to clarify are you using the latest poky edison branch? Which meta-intel branch/tag are you using?
Cheers,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 40 lines · Joshua Lock
Quoted 37 lines · jfabernathy
Quoted 35 lines · Joshua Lock
Quoted 20 lines · jfabernathy
Quoted 19 lines · Bruce Ashfield
Quoted 7 lines · jfabernathy
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same, old same old. I tried the standard unchanged SRCREV and
also tried the latest.I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there
shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).Perhaps Josh knows if anything was pushed to edison ?
Quoted 7 lines
Quoted 3 lines
Cheers,
Bruce
I'm retesting on the tarballs again. If successful I'll try git version of edison. I started today with complete new clone of poky and meta-intel.
The Edison branch has been updated today for the upcoming 1.1 release, did you pull the updates?
Other than meta-intel are you using any other layers? I will try and reproduce here.
Quoted 7 lines
Quoted 4 lines
I tried some stuff this morning like switching branches, then doing git pulls, etc. I was getting such bad results, I figured I had screwed up. I re-cloned both poky and meta-intel earlier today. Maybe around 12 noon EST.
This sounds like meta-intel and the Edison updates aren't getting along. Just to clarify are you using the latest poky edison branch? Which meta-intel branch/tag are you using?
What I did after cloning Poky and Meta-intel, I cheched out edison in both poky and meta-intel direction using the same command that they use in Developer Manual Appendix A.
Quoted 2 lines
Cheers,
Joshua
Quoted 47 lines · jfabernathy
Quoted 46 lines · Joshua Lock
Quoted 42 lines · jfabernathy
Quoted 30 lines · Joshua Lock
Quoted 20 lines · jfabernathy
Quoted 19 lines · Bruce Ashfield
Quoted 7 lines · jfabernathy
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same, old same old. I tried the standard unchanged SRCREV and
also tried the latest.I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there
shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).Perhaps Josh knows if anything was pushed to edison ?
Quoted 8 lines
Quoted 3 lines
Cheers,
Bruce
I'm retesting on the tarballs again. If successful I'll try git version
of edison. I started today with complete new clone of poky and meta-intel.Quoted 6 lines
The Edison branch has been updated today for the upcoming 1.1 release, did you pull the updates?
Other than meta-intel are you using any other layers? I will try and reproduce here.
I tried some stuff this morning like switching branches, then doing git pulls, etc. I was getting such bad results, I figured I had screwed up. I re-cloned both poky and meta-intel earlier today. Maybe around 12 noon EST.
Quoted 7 lines
Quoted 4 lines
This sounds like meta-intel and the Edison updates aren't getting along. Just to clarify are you using the latest poky edison branch? Which meta-intel branch/tag are you using?
What I did after cloning Poky and Meta-intel, I cheched out edison in both poky and meta-intel direction using the same command that they use in Developer Manual Appendix A.
Right. I think we'll need to change the manual, at least to make it clear that the branches are not static.
As an aside to that I will see if I can figure out what's causing the error you reported.
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 40 lines · Joshua Lock
Quoted 37 lines · jfabernathy
Quoted 35 lines · Joshua Lock
Quoted 20 lines · jfabernathy
Quoted 19 lines · Bruce Ashfield
Quoted 7 lines · jfabernathy
It seems that something happened today. I could not complete a build on
edison branch for meta-cedartrail. I copied it to meta-mycdv, but other
than that same, old same old. I tried the standard unchanged SRCREV and
also tried the latest.I changed the main yocto 1.2 3.0 kernel repository to 3.0, and pushed some other kernel
changes. But if you are purely on edison, and aren't using meta-kernel-dev there
shouldn't have been any fallout from those changes. (I built 3.0 several times today
myself).Perhaps Josh knows if anything was pushed to edison ?
Quoted 7 lines
Quoted 3 lines
Cheers,
Bruce
I'm retesting on the tarballs again. If successful I'll try git version of edison. I started today with complete new clone of poky and meta-intel.
The Edison branch has been updated today for the upcoming 1.1 release, did you pull the updates?
Other than meta-intel are you using any other layers? I will try and reproduce here.
Quoted 7 lines
Quoted 4 lines
I tried some stuff this morning like switching branches, then doing git pulls, etc. I was getting such bad results, I figured I had screwed up. I re-cloned both poky and meta-intel earlier today. Maybe around 12 noon EST.
This sounds like meta-intel and the Edison updates aren't getting along. Just to clarify are you using the latest poky edison branch? Which meta-intel branch/tag are you using?
Could my having a local download directory that is used on all bakes cause this problem???
Quoted 2 lines
Cheers,
Joshua
Quoted 2 lines · jfabernathy
Could my having a local download directory that is used on all bakes cause this problem???
Not at all, that's fully supported.
Cheers,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre