ything! ;-)
(I'm only half-kidding, actually -- FWIW, I use hwloc for everything these
days. The logical ordering alone makes it worthwhile. The simplicity of
hwloc-bind's socket:X,core:Y is even more lovely. ...etc.)
--
Jeff Squyres
jsquy...@cisco.com<mailto
org>
https://lists.open-mpi.org/mailman/listinfo/hwloc-devel
--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
___
hwloc-devel mailing list
hwloc-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/hwloc-devel
FYI -- same applies for hwloc commit emails.
Begin forwarded message:
From: "Jeff Squyres \(jsquyres\) via ompi-commits"
mailto:ompi-comm...@lists.open-mpi.org>>
Subject: [OMPI commits] Commit emails
Date: April 26, 2019 at 10:28:30 AM EDT
To: "ompi-comm...@lists.open-mpi
t may well have been the last sticking
point that allowed us to move Open MPI to C99.
--
Jeff Squyres
jsquy...@cisco.com
___
hwloc-devel mailing list
hwloc-devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/hwloc-devel
ate.
>
> Let me know if you are interested in seeing any changes, or have any
> problems, in python-hwloc.
>
> regards,
> --Guy Streeter
>
> _______
> hwloc-devel mailing list
> hwloc-devel@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/h
onsortium.org/mailman/listinfo/hwloc-devel
--
Jeff Squyres
jsquy...@cisco.com
___
hwloc-devel mailing list
hwloc-devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/hwloc-devel
l don't think that "likely" is bad to
have, but this likely isn't worth arguing about.
(I'll likely just disable the email hook, re-commit "likely", re-enable the
email hook, and YOU'LL NEVER KNOW! WORLD DOMINATION!! ;-) )
(and now that I'm consciou
nd I am pretty sure it's
> not the first time it happens. There are no archives for this ML, do we
> have a way to see the logs of the emailing script that runs on github ?
>
> Brice
>
>
>
> Le 08/02/2017 16:19, Jeff Squyres (jsquyres) a écrit :
>> On Feb 7,
On Feb 7, 2017, at 12:12 PM, Jeff Squyres (jsquyres) wrote:
>
> Fair enough, but the test itself is just a switch/case statement -- it's not
> an actual test to see if the system supports binding or not. Hence, hedging
> the warning message a little seemed reasonable.
I
ing or not. Hence, hedging the
warning message a little seemed reasonable.
--
Jeff Squyres
jsquy...@cisco.com
___
hwloc-devel mailing list
hwloc-devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/hwloc-devel
s the issue.
We haven't chosen to do this for most Open MPI projects, but it might be a
possibility. If nothing else, if it's a serious problem for your users, you
could duplicate posting the hwloc tarballs to
https://github.com/open-mpi/hwloc/releases.
--
Jeff Squyres
jsquy...@cisc
ailable under
https://www.open-mpi.org/community/lists/ (so that we don't break lots of old
links from around the web), but they are frozen. No new messages have been
added to the frozen archive since late July 2016 or so.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal
e to work). We will
eventually remove links to this archive from the Open MPI web site, and replace
them with links to the new Mail Archive. Hopefully, the old archive will
eventually disappear from Google, and will effectively be replaced by the new
copies of the same mails at mail-archive.com.
--
...and we're back.
NOTE: the email address for this list has now changed! It is now
@lists.open-mpi.org (it used to be @open-mpi.org).
PLEASE UPDATE YOUR CONTACTS AND MAIL CLIENT FILTERS!
> On Jul 27, 2016, at 12:01 PM, Jeff Squyres (jsquyres)
> wrote:
>
> We are b
We unfortunately ran into major issues while trying to migrate these lists, and
have therefore restored them back on the Indiana U servers until we try the
migration again.
Sorry for the hassle folks; stay tuned!
> On Jul 20, 2016, at 10:28 AM, Jeff Squyres (jsquyres)
> wrote:
>
We are beginning the list migration process; this list will be suspended while
it is in transit to a new home.
We can't predict the exact timing of the migration -- hopefully it'll only take
a few hours.
See you on the other side!
--
Jeff Squyres
jsquy...@cisco.com
For corpo
l continue to be available,
but they'll be frozen -- no new messages will be added there. Specifically:
links to old posts will continue to work.
2. New web archives for all the lists -- to include all the old posts -- will
become available elsewhere. Specifics will be included in
/ maintained along side the autotools
configure/build system, and it was continually out of date :-( )
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ctual releases, but the OMPI v1.8 series is coming to a
close, so I think that this is ok.
This PR is actually for OMPI master; once it shakes out ok on master, we'll PR
it over to OMPI v1.8. Once that has all completed, we'll likely want to
upgrade OMPI master to hwloc v1.10.1
s: have you see this Lhwloc1 dup symbol issue before?
I ask because on OMPI master, we can just upgrade to hwloc 1.10. But in OMPI
v1.8.x, it's less attractive to upgrade -- it would be cool if there was a
simple fix that we could backport/patch the hwloc 1.9.1 in OMPI 1.8.x with the
fix
=
>
> Your friendly daemon,
> Cyrador
> ___
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-
On Feb 14, 2015, at 8:57 AM, Brice Goglin wrote:
>> Brice: do you have a nightly coverity submission script running somewhere?
>
> No, I just run it manually from time to time.
Do you want it to run automated? We can run the script at IU.
--
Jeff Squyres
jsquy...@cisco.com
F
I added a bunch of components into the hwloc coverity setup, as well as a dummy
model file (so that coverity doesn't complain that hwloc is not fully
configured).
Brice: do you have a nightly coverity submission script running somewhere?
--
Jeff Squyres
jsquy...@cisco.com
For corporate
ID_EXP);
> +
> if (offset > 0 && offset + 20 /* size of PCI express block up to link
> status */ <= CONFIG_SPACE_CACHESIZE)
> hwloc_pci_find_linkspeed(config_space_cache, offset,
> &obj->attr->pcidev.linkspeed);
>
>
>
> ---
>
> Summary of changes:
> hwloc/topology-pci.c | 41 ++---
> 1 file changed, 22 insertions(+), 19 deletions(-)
>
>
> hooks/post-receive
> --
> open-mpi/hwloc
> ___
> hwloc-commits mailing list
> hwloc-comm...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-commits
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
ology items, including the differences between the
different caches.
Perhaps it would be sufficient to be able to combine the type and the cache
type together somehow -- e.g., the cache type could be bit-shifted up above the
type bits, and then you could switch/case on the combined value...? (waving
hands furiously...)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
as a good point about "where will it end?".
But I also agree that it's pretty annoying (and Ralph has [rightfully]
complained a bunch) to have to special-case the check for the various caches --
it has caused a bunch of code churn in OMPI.
How about making enums for L1 through L5? T
Errr... I got the patch slightly wrong. The one added line should include the
".$HWLOC_RELEASE_VERSION" at the end. You get the idea...
On Oct 1, 2014, at 8:50 PM, Jeff Squyres (jsquyres) wrote:
> We just changed the version numbering scheme over in OMPI to always be
> &q
SION"
-fi
+HWLOC_VERSION="$HWLOC_MAJOR_VERSION.$HWLOC_MINOR_VERSION"
HWLOC_VERSION="${HWLOC_VERSION}${HWLOC_GREEK_VERSION}"
# If HWLOC_SNAPSHOT=1, then use HWLOC_SNAPSHOT_VERSION
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
e...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
> Link to this post:
> http://www.open-mpi.org/community/lists/hwloc-devel/2014/09/4242.php
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
de
> gets DIMM info somehow.
Back in Nehalem days, it wasn't possible to map Linux kernel "physical" memory
back to individual DIMMs (because the BIOS could/would introduce another layer
of kernel<-->DIMM mapping that the kernel might not be aware of).
Has that chang
On Sep 22, 2014, at 4:46 PM, Jeff Squyres (jsquyres) wrote:
>>> I am not able to figure out how to read Hard drive details, for e.g.,
>>> the content provided by hdparm application.
>>>
>>> My first question is, is it possible to read this using hwloc? If
annotation/review tools -- depending on
the situation, you may want to use (e.g., for fine-grained, detailed replies)
those instead of replying to hwloc-commits mails, anyway.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal
ired via gitdub (not cron)
***NOTE: the mailing list is now hwloc-commits (not hwloc-svn)
So I think we're finally 100% Github for hwloc.
Enjoy!
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Cool. I'm going to wait until I hear from Brice (I think he might be
traveling?); I don't want to spam him with a zillion emails.
On Sep 12, 2014, at 7:58 AM, Samuel Thibault wrote:
> Jeff Squyres (jsquyres), le Fri 12 Sep 2014 10:44:03 +, a écrit :
>> I did a test imp
minutes because there's only a few dozen tickets), you can set your watching
back to the normal level.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Yoinks!
Autocomplete in my email client sent this to the wrong list... hwloc conversion
is already done. This message was meant for the main Open MPI developers list,
not the hwloc list.
Sorry for the noise...
On Sep 9, 2014, at 12:03 PM, Jeff Squyres (jsquyres) wrote:
> As part of
have updated
information for everyone for next Tuesday's call.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
e);
> + sprintf(tmp, "%llu", (unsigned long long)
> diff->obj_attr.diff.ui64.oldvalue);
> state.new_prop(&state, "obj_attr_oldvalue", tmp);
> - sprintf(tmp, "%llu", (unsigned long long)
> diff->obj_attr.diff.uint64.newvalue);
> + sprintf(tmp, "%llu", (unsigned long long)
> diff->obj_attr.diff.ui64.newvalue);
> state.new_prop(&state, "obj_attr_newvalue", tmp);
> break;
> case HWLOC_TOPOLOGY_DIFF_OBJ_ATTR_NAME:
> ___
> svn-full mailing list
> svn-f...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/svn-full
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
The hwloc wiki -- all 5 pages of it :-) -- is now officially on github:
https://github.com/open-mpi/hwloc/wiki
The Trac wiki is now deprecated.
(...conversion of Trac tickets is still in the works...)
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http
least some of the
content needs to be updated for Github), I can move it to the real hwloc Github
wiki.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Good enough; thanks for the refresher. :)
Sent from my phone. No type good.
> On Aug 18, 2014, at 2:07 PM, "Brice Goglin" wrote:
>
> Le 18/08/2014 20:37, Jeff Squyres (jsquyres) a écrit :
>> I notice that --enable-plugins seems to be broken -- it always ends in:
? Or have we previously embedded libltdl
(via LT_CONFIG_LTDL_DIR), and it has just bit-rotted?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
How about displaying a warning if --get is specified but a command to execute
is also specified?
Sent from my phone. No type good.
> On Aug 13, 2014, at 5:22 AM, "John Donners" wrote:
>
> Hi Brice,
>
>> On 13-08-14 10:46, Brice Goglin wrote:
>> Hello,
>>
>> Can you elaborate how you would u
so that children don't inherit it. Stevens says
+ that we should GETFD before we SETFD, so we do. */
+ flags = fcntl(root, F_GETFD, 0);
+ if (-1 == flags ||
+ -1 == fcntl(root, F_SETFD, FD_CLOEXEC | flags)) {
close(root);
root = -1;
goto out_with_data;
--
ore like:
> int prev;
> if ((-1 == (prev = fcntl(root, F_GETFD, 0)) ||
> (-1 == fcntl(root, F_SETFD, FD_CLOEXEC | prev)))
>
>
>
>
> On Wed, Apr 23, 2014 at 2:55 PM, Jeff Squyres (jsquyres)
> wrote:
> Will do.
>
> On Apr 23, 2014, at 5:52 PM, Samuel Th
Actually, I just checked around: we have some unprotected FD_CLOEXEC code in
OMPI was that committed 2010-08-24 that has never caused a problem.
So I'm not thinking it should be necessary here, either.
On Apr 23, 2014, at 5:55 PM, Jeff Squyres (jsquyres) wrote:
> Will do.
>
Will do.
On Apr 23, 2014, at 5:52 PM, Samuel Thibault wrote:
> Jeff Squyres (jsquyres), le Wed 23 Apr 2014 21:05:55 +, a écrit :
>> Any objections to this patch? In OMPI, we're seeing this fd leak into child
>> processes.
>>
>> diff --git a/src/topolog
;
+ }
#else
if (strcmp(fsroot_path, "/")) {
errno = ENOSYS;
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
time/effort to
convert. We'll also need to talk about:
- how to handle permissions on release branches (git doesn't have the same kind
of directory-based permissions that we do in SVN)
- end-of-life the bitbucket/hg mirror
Hope this helps explain the current direction. Please feel free t
README"
ls -lf $distdir/README
On Apr 7, 2014, at 6:04 PM, Brice Goglin
wrote:
> My jenkins does make distcheck on some Linux and only make check on
> others, so it should be fine on my side.
>
> Brice
>
>
>
>
> Le 08/04/2014 00:01, Jeff Squyres (jsqu
Do we care about "make dist" on Solaris?
On Apr 7, 2014, at 5:57 PM, Brice Goglin wrote:
> Same error.
> Brice
>
>
>
> Le 07/04/2014 23:43, Jeff Squyres (jsquyres) a écrit :
>> How about:
>>
>> tar c -C /home/ci/hwloc-gitclone -h -f - doc/doxy
-x -C
> /home/ci/hwloc-gitclone/build/hwloc-gitclone -f -
> tar: /dev/rmt/0: No such file or directory
>
>
>
> Le 07/04/2014 23:29, Jeff Squyres (jsquyres) a écrit :
>> --- a/config/distscript.sh
>> +++ b/config/distscript.sh
>> @@ -69,7 +69,7 @@ fi
>> #
On Apr 7, 2014, at 5:06 PM, "Jeff Squyres (jsquyres)"
wrote:
> Ok, lemme look at tar -- there's a canonical way to copy dir trees with tar;
> let me look it up...
Does this work for you? It seems to do the Right Thing for me on OS X and
Linux.
diff --git a/config/d
rce if $srcdir/doc/doxygen-doc
>is a symlink to builddir/doc/doxygen-doc.
>But it actually fails to copy the doxygen-doc tree because it
>doesn't dereference the symlink. Fix that.
>
> Brice
>
>
>
>
> Le 07/04/2014 22:59, Jeff Squyres (jsquyr
, too).
I guess we should be using something better than cp -r to copy the directory
over -- perhaps tar?
> I managed to get such a tarball without doc only once, but it
> disappeared after I added some debug commands to config/distscript.sh to
> see where doc/doxygen-doc was being deleted
>>> Looks like it's a 10 years old conflict between csh and coreutils. It's
>>> crary hwloc has to work around this very old issue, we should just stop
>>> using csh and distros that haven't fixed this :)
>>>
>>> Brice
>>>
>>
s. It's
> crary hwloc has to work around this very old issue, we should just stop
> using csh and distros that haven't fixed this :)
>
> Brice
>
> _______
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
&g
Sweet; thanks.
On Jan 10, 2014, at 12:25 PM, Brice Goglin wrote:
> Looks like we're good.
> Brice
>
>
>
> Le 10/01/2014 18:05, Jeff Squyres (jsquyres) a écrit :
>> K, will do.
>>
>> On Jan 10, 2014, at 12:00 PM, Brice Goglin
>> wrote:
&
K, will do.
On Jan 10, 2014, at 12:00 PM, Brice Goglin
wrote:
> Push it to master, we'll what regression testing at
> https://ci.inria.fr/hwloc/job/master-1-check/ thinks about it
> Brice
>
>
>
> "Jeff Squyres (jsquyres)" a écrit :
> Brice / Sa
MALIGN) &&
defined(HAVE_MEMALIGN) && defined(HAVE_MALLOC_H)
+#include
#endif
#ifdef HAVE_UNISTD_H
#include
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
I wonder if hwloc will be able to show this. Let's hope this kind of topo stuff
is exported in /sys...
http://www.theregister.co.uk/2013/11/21/intel_converging_memory_and_cpus/?utm_source=dlvr.it&utm_medium=gplus
Intel pulls up its SoCs, reveals 'integrated' memory on CPUs
Disaster recovery pr
t; utils/test-hwloc-diffpatch.sh.in | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>>
>> hooks/post-receive
>
> _______
> hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
Ok, sorry for the bazillion emails you just got, but the email script should
now send out notices for all commits on all branches now.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
> enable them on github?
>
> Brice
>
>
>
> Le 06/11/2013 15:30, Jeff Squyres (jsquyres) a écrit :
>> There was a disk problem on the IU server where the git commit message came
>> from.
>>
>> It wa
There was a disk problem on the IU server where the git commit message came
from.
It was just fixed, which is why we got the commit email so late.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
one has Xlib.h, having Xutil.h and keysym.h is not really far
> anyway.
Ok -- so you're saying we *require* all 3, right?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
them, there's extra
X11 goodies that can be used)
Is that correct? Or do we *require* all 3 header files for X11 support?
On Nov 1, 2013, at 11:20 AM, "Jeff Squyres (jsquyres)"
wrote:
> Ya -- working on a new patch, too.
>
>
> On Nov 1, 2013, at 11:10 AM, Br
Ya -- working on a new patch, too.
On Nov 1, 2013, at 11:10 AM, Brice Goglin wrote:
> Can you first find out which header and library contains XOpenDisplay()
> on your Mac?
>
> Brice
>
>
>
> Le 01/11/2013 16:01, Jeff Squyres (jsquyres) a écrit :
>> Ah; I misse
to be independent
of Cairo and GL (and therefore only once, and include the AC_DEFINE for
HWLOC_HAVE_X11)?
On Nov 1, 2013, at 10:53 AM, Samuel Thibault wrote:
> Jeff Squyres (jsquyres), le Fri 01 Nov 2013 15:12:31 +0100, a écrit :
>> Cool. Does the following patch look ok? If so, I'
rs not found, Cairo/X11 back-end disabled])
- hwloc_cairo_happy=no
-fi
-
- CFLAGS=$CFLAGS_save
- LIBS=$LIBS_save
- fi
fi
if test "x$hwloc_cairo_happy" = "xyes"; then
On Nov 1, 2013, at 10:07 AM, Samuel Thibault wrote:
> Hel
still seem
to use Cairo in lstopo (e.g., generate PDFs and PNGs).
Are there some platforms where linking Cairo depends on X11? If so, is there a
way we can discover that in configure? (because Cairo doesn't seem to need X11
on OS X for just outputting PDFs and PNGs)
--
Jeff Squyres
js
log
>> to find that number.
>
> Mmm, we don't have the commit diff any more? I found that useful, to be
> able to quickly see what happened exactly.
>
> Samuel
> ___
> hwloc-svn mailing list
> hwloc-...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-svn
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
rm -rf your local clone and pull down a fresh one.
Big apologies to everyone for all this hassle; it was my mistake that caused
this kerfuffle (bonus to everyone: use kerfuffle in a sentence today).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com
On Oct 3, 2013, at 1:01 PM, Jeff Squyres (jsquyres) wrote:
> Yes; I replayed on the master, but not v1.7 yet. I'll go do that now...
Ok, I replayed on v1.7 and pushed.
As an added bonus, I figured out where I went wrong and screwed up the original
github/open-mpi/hwloc github rep
On Oct 3, 2013, at 12:31 PM, Brice Goglin wrote:
> The master branch looks good to me, and the list of branches looks fine too.
Good.
> v1.7 misses the last git commits, but I guess you didn't update it yet.
Yes; I replayed on the master, but not v1.7 yet. I'll go do that
sting
githib/open-mpi/hwloc and replace it with this one.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
On Oct 3, 2013, at 6:41 AM, Brice Goglin wrote:
> It was likely moved to the attic. If svn2git doesn't find it, that's
> fine, I still have it in my archives in case we ever want it (very
> unlikely).
Ah, ok.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal infor
wloc git repo because nothing
tremendously important has happened since the conversion (we can just replay
the script update commits -- it'll be a little painful, but do-able).
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
hat
is "re-used", so to speak everywhere); the rest is processing that we do for
whatever reason that the tarball is being built.
Any other thoughts on how we can simplify things?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
you want to keep -- just the cuda branch? -- and let
me chat with Dave to see how to get that back.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
> people-friendly for #2 (nightly tarballs).
Fair enough.
That being said, when we tell users to get a nightly tarball (e.g., to get a
bug fix), my experience is that they don't know/care about the nightly tarball
numbering scheme: they always just get the most recent version.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
the attached one for Open-MX and KNEM. Not sure I tried many of
> them, but this one worked fine so far. It generates messages such as:
>
> http://lists.gforge.inria.fr/pipermail/knem-commits/2013-July/000465.html
> I don't think it truncates the diff yet. We may want some separators
>
I pinged IU. We ran into this problem during the svn->git transition, but I
thought DongInn fixed it. Sorry...
On Sep 28, 2013, at 8:23 AM, Brice Goglin wrote:
> I can't login on Trac. Requested a new password, doesn't work either.
>
> Brice
>
>
> Le
; hwloc-devel mailing list
> hwloc-de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/hwloc-devel
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
pi/hwloc/settings/hooks; scroll down to
"Email"). There's *very* little configuration available:
- the address to send to
- an email address secret
- what address to send from
There's no option for diffs (!), and no option to customize the mail/subject.
:-\
Do you have a fav
Ok, the infrastructure is now updated. I've generated the first snapshot
tarballs in http://www.open-mpi.org/software/hwloc/nightly/. Nightly snapshots
for <=v1.6 have all been removed.
Git is fully open for business. Enjoy.
--
Jeff Squyres
jsquy...@cisco.com
For corpora
argely as it did before: it'll make hwloc-.tar.*.
The latter is being heavily updated to basically use "git describe".
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
*upcoming* version".
I think that this is ok (other projects use this "git describe" kind of
behavior for their nightly snapshots), but this is a change from what we used
to do, so I wanted to call it out specifically.
Are you guys ok with this?
(note: I'm still muck
tinue working on the
nightly tarball script tomorrow.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
onversion
4. DongInn will use the new hwloc github to convert to a new hwloc github trac
5. We'll do some sanity checking to make sure it's all working
6. We'll send an "all clear" email, and we'll move on in life using github+trac
--
Jeff Squyres
jsquy...@cisco.com
For
ce
>
>
>
> Le 23/09/2013 20:36, Jeff Squyres (jsquyres) a écrit :
>> Did you guys want to try to git commits and see them affect trac, etc.?
>>
>> I'm thinking that getting you 2 guys happy with the github <--> trac
>> interaction is the last step
The nightly tarballs were broken for a few days after IU moved the build
machine to a different server.
They should now be fixed -- the OMPI 1.9 tarball was generated a few minutes
ago; the others are being built right now.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information
10:07 AM, Jeff Squyres (jsquyres) wrote:
> Added both of you.
>
> On Sep 7, 2013, at 2:52 AM, Samuel Thibault wrote:
>
>> Jeff Squyres (jsquyres), le Sat 07 Sep 2013 00:04:13 +0200, a écrit :
>>> What are your github IDs?
>>
>> sthibaul
>>
>> S
IU moved the nightly build cron jobs to a new machine today, and they failed.
I'm manually running the build cron jobs on the old build machine (eddie) right
now.
I've alerted IU to what I think the error was in the move; hopefully they'll be
able to fix it over the weekend.
-
Added both of you.
On Sep 7, 2013, at 2:52 AM, Samuel Thibault wrote:
> Jeff Squyres (jsquyres), le Sat 07 Sep 2013 00:04:13 +0200, a écrit :
>> What are your github IDs?
>
> sthibaul
>
> Samuel
> ___
> hwloc-devel mail
ward with github and leave SVN behind.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
nically it's still
> correct ;-). But I blame Fortran for this oversight.
LOL!
(that was an MPI Forum/inside joke for those of you wondering WTF it meant :-) )
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
tool, you may include this file under the
same distribution terms that you use for the rest of that program.
-
This special exception is included in every single file under src/libltdl
except README and COPYING.LIB.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go
it until the migration is done.
Please let me know if you have any questions or issues about this migration.
Regards,
--
- DongInn
---
CREST System administrator
Indiana University
Bloomington, IN
--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
For
ns are obviously less important, keep these out of
> hwloc.h (just like the ones in hwloc/helper.h currently)
> * only keep the strict minimum (types?) in hwloc.h ?
>
> Brice
>
> ___
> hwloc-devel mailing list
> hwloc-de...@open-m
1 - 100 of 821 matches
Mail list logo
